Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

[VMC on AWS] Handling different vCenter Alarms in VMware Cloud on AWS (77191)

Last Updated: 10/26/2023Categories: InformationalTotal Views: 401Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Purpose

This article provides information about the handling of different vCenter Alarms observed in VMC on AWS.

Resolution

1)Virtual Machine (VM) Consolidation Needed status :

Cause: This could happen if a snapshot file exists and is not recognized by Snapshot Manager.
Solution: Consolidate the snapshots
Go to VM > Snapshot>Consolidation >Consolidate Snapshots.

Note: Before consolidating have a complete backup of the Virtual Machine.

Reference Link: https://kb.vmware.com/s/article/1002310

2) Root Disk Exhaustion on vCenter :
It is a warning alert that is observed whenever the Disk space reaches its maximum capacity during any of the operations which are expected to last for some time.
This alert is cosmetic during such cases and thus can be safely ignored.
However, if the Disk Space usage is expected to be high(i.e >80%) all the time, kindly reach out to VMware Cloud on AWS Technical Chat Support or File a Service Request using the following document .

3)vSphere HA virtual machine Monitoring error :
This alarm is triggered when vSphere HA cannot reset the virtual machine.

To clear the alarm, disable and enable VM monitoring by performing the steps below:

1.     Disable VM monitoring.

2.     Acknowledge and reset the alarm to green. See Acknowledge Triggered Alarms.

3.     Enable VM monitoring. See Enable VM Monitoring.

Reference Links :
https://kb.vmware.com/s/article/2064236

4) vSAN Disk Balance :
Cause: This alert is observed when the disk usage in the witness is 0.

Solution :

This is a known cosmetic issue in VMware vSAN and can be safely ignored.

To avoid this issue, disable the vCenter alarm for disk balance health check using the below steps:

1.     Navigate to vCenter > Monitor > Issues > Alarm Definition.

2.     Disable the vSAN Health Alarm:
"vSAN Disk Balance".

3. Avoid disabling it on any cluster that is reaching 70 % of space usage. Disk rebalance algorithm has been
optimized in 6.5 U2 and higher version and are highly recommended.

Reference Link: https://kb.vmware.com/s/article/2144278

5) Errors occurred on the disk of a vSAN host :

The alarm is triggered by the following event: esx.problem.vob.vsan.lsom.diskerror: Virtual SAN devices encounter a permanent error when devices are not readable or writeable.

6) VMware vAPI endpoint Service Health alarm:
This alarm is triggered when old endpoint entries are observed in the lookup service.

Cause :
When vAPI Endpoint service is re-configuring itself and an inappropriately handled exception occurs, it enters a state where a broken spring bean is saved, every subsequent reconfiguration fails and the service reports yellow status at that point.

Workaround: Restart the API Endpoint service to clear the faulty configuration state.
Reference Link: https://kb.vmware.com/s/article/2144715

8)vSphere Health detected new issues in your environment:
This alarm is observed when the current status of the Customer Experience Improvement Program (CEIP) is disabled. Online health checks are not available if CEIP is disabled.

Resolution: There is no negative impact on vCenter.
This alarm can be disabled in the vCenter :
vCenter > Configure > Alarm Definitions > DISABLE or ignore the alarm

Reference Link: https://blogs.vmware.com/vsphere/2019/01/understanding-vsphere-health.html

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
Download and Install VMware Fusion (2014097)

KB
•
vMotion が ”Module 'MonitorLoop' power on failed” エラーで失敗する (93182)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Cloud on AWS

Related Versions:

Take Our Survey

Support Assistant